Add Bazel RBE integration guide (DI-574)#237
Open
celanthe wants to merge 8 commits into
Open
Conversation
New customer-facing page covering Orka as the macOS worker layer in a Bazel Remote Build Execution setup. Covers two paths: open-source buildfarm (recommended) and BuildBuddy (for teams already using it). Includes multi-worker deployment, GitHub Actions workflow automation, LaunchDaemon auto-start pattern, and persistent cache setup. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
- Expand bare-metal re-imaging explanation (DEP, Xcode, hours not seconds) - Rename Image versioning to Pinned build environments with Xcode drift framing - Add isolation bullet explaining cross-project contamination risk - Tighten worker pool scaling bullet - Source: competitive research from MPD-81 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Switch server and worker startup from `bazelisk run` (rebuilds from source on every restart) to pre-built JARs run with `java -jar`, matching the verified approach in the quickstart. Also replace config.minimal.yml references with flat YAML configs — the !include-based examples format does not work at runtime. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Adds the single-VM quickstart guide (bazel-rbe-quickstart.mdx) verified end-to-end against a live Orka cluster. Also fixes the start-worker.sh startup script template in bazel-rbe.mdx: the script was setting publicName to `:8981` (no hostname), causing every findMissingBlobs call to fail with "Invalid DNS name: :8981". Fixed to use MY_IP=127.0.0.1 and rewrite publicName dynamically on each boot. LaunchDaemon plist updated to match actual script path and add UserName/WorkingDirectory. Closes DI-574 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Fix GitHub Actions workflow: orka3 user set-token for auth, --config flag (not --vm-config), remove non-existent --endpoint/--token flags - Correct Bazel version note: .bazelversion pin is for building buildfarm from source, not for the client (8.x and 9.x both work as clients) - Replace Harbor OCI registry reference with accurate language: Orka supports any OCI-compatible registry (ghcr.io, ECR, etc.) - Remove all em dashes from both pages Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Orka 3.5+ bridge networking gives VMs a routable IP on the host network, so they can reach each other across nodes directly. The previous note implied cross-node connectivity was always blocked (NAT-only assumption). Updated to cover both bridge and NAT mode and point to support for cluster network config confirmation. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
/orka/managing-vms/ directory does not exist. Correct paths: - image-caching -> /orka/orka-resources/image-caching - vm-configs -> /orka/orka3-cli-reference/vm-deployment-and-configuration Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two new pages covering Bazel RBE with Orka-hosted macOS workers using open-source buildfarm.
bazel-rbe-quickstart.mdxwalks through a working single-VM PoC: Redis, buildfarm server, and worker all on one Orka VM, with the Bazel client connecting over an SSH tunnel. Tested on my cluster: Cold build3 remote, clean expunge + rebuild3 remote cache hit.bazel-rbe.mdxcovers the production path: separate Linux server VM, Orka worker pool, GitHub Actions workflow for ephemeral workers, and BuildBuddy as an alternative control plane.A few things in here worth your eyes specifically:
start-worker.shLaunchDaemon pattern and howpublicNamegets written on bootvm_network_mode: bridgeincluster.yml); NAT fallback is documented for clusters without itBuildBuddy section needs Heath to review before this merges.
Closes DI-574